Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

Notes/Domino 6 and 7 Forum

Notes/Domino 6 and 7 Forum


  

PreviousPrevious NextNext


~Tony Minponeveretsi 9.May.03 09:01 AM a Web browser
Domino Server 6.0.1 Linux - SuSE


When creating a new replica via the adminp to a decentralized server, the replica stub cannot be replicated, because the ACL has been changed by the decentralised server. Enforce consistent ACL is activated for the database.

Details:
After the stub has been created on the decentralised server by the adminp of the manager server (hub server), the decentralised server updates the _Default_ entry, then adds itsleft (as server) to the ACL, then updates the default entry again, then adds the rest of the ACL entries (analog to the ACL of the hub server) and then!!! at the end -> 1. removes itself from the ACL, then adds itself (with identical rights as before) to the ACL!!! Thereafter the ACL is not consistent anymore, and the rest of the replication cannot proceed!
I had specifically added the decentralised server to the ACL with manager access to avoid any problems with group recognition.
The decentralised servers OS time is in another timezone (one hour difference) and Domino pulls its time from the OS (server doc).
Both servers have the same Domino Directory!

If I switch off consistent ACL, the DB is able to replicate.
Why does the decentralised server change the ACL??

Could this be a bug??

Update: I have removed manager rights for dec.srv from the ACL (only designer). Via adminp from hub server new replica creation request. The hub server creates the replica stub on the spoke server. the spoke server changes the ACL. It adds itself as manager to the ACL and then adds the other ACL entries.
In the server document, the hub server AND the spoke server are admins (Security\Administrators\Administrators). They are both NOT FullAccessAdmins (at least not set in the server doc).

To my understanding, following happens:
the adminp db on the hub server executes the "create replica" command and adds a replica stub on the spoke server. the spoke server then chnages the ACL. Thereafter the hub server sees, that the ACL has been changed, and thus returns the error: "cannot maintain uniform control list accorss replicas"
Thereafter, replication cannot proceed.


I would be very, very thankful for any suggestions or solutions.

Regards
Andreas






Creating new replica via AdminP - P... (~Tony Minponeve... 9.May.03)
. . RE: Creating new replica via AdminP... (~Tony Frokizenf... 9.May.03)
. . . . RE: Creating new replica via AdminP... (~Tip Asaresakon... 12.Sep.03)
. . RE: Creating new replica via AdminP... (~Tony Minponeve... 19.May.03)
. . . . RE: Creating new replica via AdminP... (~Tony Frokizenf... 19.May.03)





  Document options
Print this pagePrint this page

 Search this forum

  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Category
Platform
Release
Advanced search

 RSS feedsRSS
All forum posts RSS
All main topics RSS